Move trainer.step() before metric.update to overlap between backward pass and allreduce #1609
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
metric.update()
is a sync call and it was preventing the overlap between communication and computation since it was present betweenloss.backward()
andtrainer.step()
.metric.update()
aftertrainer.step()
to overlap communication and computation. Hence, the correct order isforward pass -> calculate loss -> backward pass -> allreduce -> metric update
.train_mask_rcnn.py
script.